-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Embedded key loader #82
base: main
Are you sure you want to change the base?
Conversation
demonsh
commented
Dec 26, 2024
- NewEmbeddedKeyLoader with embedded verification keys for:
- authV2.json
- credentialAtomicQueryMTPV2.json
- credentialAtomicQueryMTPV2OnChain.json
- credentialAtomicQuerySigV2.json
- credentialAtomicQuerySigV2OnChain.json
- credentialAtomicQueryV3-beta.1.json
- credentialAtomicQueryV3OnChain-beta.1.json
- linkedMultiQuery10-beta.1.json
- Updated readme
- added configuration for NewEmbeddedKeyLoader - added examples for supported networks - minor improvements and links to the resources added
} | ||
return key, nil | ||
} | ||
slog.Warn("failed to load key from custom loader", "circuit_id", id, "error", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm... If the user of the library explicitly provides the custom key loader, I suppose he definitely wants to use keys from this key loader. Not the embedded ones. In this case I would expect to return the error here instead of just returning embedded keys with warning.
@@ -0,0 +1,104 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about renaming the loaders/keys directory to loaders/verification_keys? I didn’t immediately understand the purpose of these JSON files.